|
WarpUP - Problem Solving These tips are for version 3.x only. Version 4.0 should handle this automatically during the installation process. |
 Sometimes
the usage of WarpUP comes with some problems, that are mostly caused by the firmware of the specific turboboards.
This document provides you with some tips on how such problems can be solved.It can be said that most of the problems appear when using a BlizzardPPC turboboard for the A1200, because this is the only one that contains firmware that starts the ppc.library on boot-up of the system, and can cause many problems with WarpUP in doing so. In spite of the co-operation promise made last year, it is until this day impossible to boot WarpUP in a clean way on BlizzardPPC systems. Added to this is the danger, that by every upgrade of the firmware (Flash-ROM) new problems with WarpUP will appear, just as it has already happened in the past. To be able to use WarpUP successfully, WarpUP 3.1 (powerpc.library V14.6) must be installed, because only this version is able to solve all problems with BlizzardPPC FlashROM. Then it is really necessary that some environment variables be set correctly. With the install script that comes with the WarpUP package, most of these variables are being set. Some of them have to be set by hand though, like for instance graphics card address space. Please proceed as outlined below: First the variable 'powerpc/terminator' must be set to the value 2: setenv powerpc/terminator 2 copy env:powerpc/terminator envarc:powerpc Users of CyberVisionPPC / BVisionPPC graphiccards must tell WarpOS the address space of the graphics card, since there is no other way to pass this address to WarpOS. If this configuration is not being made, this would mean among other things, that software such as the 3D driver system 'Warp3D' can't function in the PPC version. To do this, the following ENV variables must be set: setenv powerpc/force 1 setenv powerpc/gfxaddr $e0000000 copy env:powerpc/force envarc:powerpc copy env:powerpc/gfxaddr envarc:powerpc Some people have by mistake set the debug variable of WarpUP, which causes all WarpUP application to run extremely slow, since a protocol is being made of every function call. This needs to be corrected: setenv powerpc/debug 0 copy env:powerpc/debug envarc:powerpc It has also been reported, that the 'powerpc/memprot' variable has caused trouble. It should be set to 0: setenv powerpc/memprot 0 copy env:powerpc/memprot envarc:powerpc Users should be careful not to run PowerUP applications on boot-up of WarpUP. Specially CyberGfx PPC should not be installed. We recommend installation of the 68K version, since the PPC version doesn't contain any PPC code, and because of this doesn't speed anything up. It should also be considered, that background programs can in theory also use the ppc.library. Among these are for instance datatypes. If for instance you display background graphics on your Workbench, it could be, that redrawing the background graphic is being done using a PowerPC optimized datatype, which of course causes the system to crash, if you deactivate the ppc.library. Should you still fail to boot WarpUP in spite of all these tips, we ask that you report this to us. The best way to do this is by writing an email to s.jordan@haage-partner.com. Usually this will be answered as soon as it is received. With the release of the next version we hope to eliminate even more problems, and to answer request of many WarpUP developers. We are very open towards further recommendations concerning further development of WarpUP. Please write us. It is still desirable that the skeleton conditions are being made to allow WarpUP to boot in a clean way on every system, which would specifically mean removing the ppc.library out off the Flash-ROM of the specific hardware. Many thanks to Dirk Harlaar for this translation. |
|
Free choice PPC kernel petition |
 |
|
|
|
